Cargo aerial delivery systems and related methods

ABSTRACT

Cargo aerial delivery systems for delivering one or more delivery items and related methods. A cargo aerial delivery system may include a cargo container configured to carry the delivery item(s) and an unmanned aerial vehicle (UAV) configured to carry the cargo container to delivery destinations of the delivery items. The cargo container may include a programmable device that stores manifest information regarding the delivery item(s) and a local communication mode configured to convey delivery information from the cargo container to the UAV. A method of utilizing a cargo aerial delivery system may include loading delivery item(s) into a container body of a cargo container, entering manifest information into a programmable device, operatively engaging the cargo container with a UAV, generating a delivery itinerary, transporting the cargo container with the UAV according to the delivery itinerary, and unloading each delivery item at the respective delivery destination.

FIELD

The present disclosure relates to cargo aerial delivery systems andrelated methods.

BACKGROUND

Owing to advances in automated aerial vehicle technology, transportingdelivery items autonomously via unmanned aerial vehicles (UAVs) isincreasingly practical. However, coordinating delivery of a plurality ofdelivery items utilizing a plurality of UAVs may introduce logisticalchallenges. For example, in a logistics operation that includes aplurality of UAVs each configured to carry one of a plurality of cargocontainers, the ability to pair a given cargo container to a given UAVmay be constrained by a predetermined configuration of the UAV and/or bya need to provide the UAV with delivery instructions corresponding tothe cargo container. Accounting for a variable payload of delivery itemscontained within a given cargo container serves to compound suchchallenges.

SUMMARY

Cargo aerial delivery systems for delivering one or more delivery itemsand related methods are disclosed herein. A cargo aerial delivery systemmay include a cargo container configured to carry the one or moredelivery items and an unmanned aerial vehicle (UAV) configured to carrythe cargo container to each of one or more delivery destinationscorresponding to the delivery items. The cargo container may include aprogrammable device that stores manifest information regarding eachdelivery item. The manifest information includes item destinationinformation that represents the delivery destination of each deliveryitem. The cargo aerial delivery system further utilizes a localcommunication mode configured to convey delivery information, which isat least partially based upon the item destination information, from thecargo container to the UAV.

A method of utilizing a cargo aerial delivery system to deliver one ormore delivery items to respective delivery destinations may includeloading the delivery item(s) into a container body of a cargo containerand entering manifest information regarding each delivery item into aprogrammable device of the cargo container. The method additionally mayinclude operatively engaging the cargo container with a UAV, generatinga delivery itinerary for delivering the delivery item(s) to therespective delivery destinations, transporting the cargo container withthe UAV according to the delivery itinerary, and unloading each deliveryitem at the respective delivery destination.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic side elevation view representing examples of cargoaerial delivery systems according to the present disclosure.

FIG. 2 is a schematic diagram representing an example of utilizing cargoaerial delivery systems according to the present disclosure.

FIG. 3 is a top side isometric view representing an example of a cargoaerial delivery system with a cargo container positioned outside of anunmanned aerial vehicle (UAV) according to the present disclosure.

FIG. 4 is a top side isometric view representing the cargo aerialdelivery system of FIG. 3 with the cargo container received within theUAV.

FIG. 5 is bottom rear isometric view representing the cargo aerialdelivery system of FIGS. 3-4 with the cargo container positioned outsideof the UAV.

FIG. 6 is a flowchart schematically representing methods of utilizingcargo aerial delivery systems according to the present disclosure.

DESCRIPTION

FIGS. 1-6 provide illustrative, non-exclusive examples of cargo aerialdelivery systems 10 for delivering one or more delivery items 20 torespective delivery destinations 22 and/or of cargo container 100 forcarrying one or more delivery items 20, according to the presentdisclosure. Elements that serve a similar, or at least substantiallysimilar, purpose are labeled with like numbers in each of FIGS. 1-6, andthese elements may not be discussed in detail herein with reference toeach of FIGS. 1-6. Similarly, all elements may not be labeled in each ofFIGS. 1-6, but reference numerals associated therewith may be utilizedherein for consistency. Elements, components, and/or features that arediscussed herein with reference to one or more of FIGS. 1-6 may beincluded in and/or utilized with any of FIGS. 1-6 without departing fromthe scope of the present disclosure. Generally, in the figures, elementsthat are likely to be included in a given example are illustrated insolid lines, while elements that are optional to a given example areillustrated in broken lines. However, elements that are illustrated insolid lines are not essential to all examples of the present disclosure,and an element shown in solid lines may be omitted from a given examplewithout departing from the scope of the present disclosure.

FIG. 1 schematically illustrates examples of cargo aerial deliverysystems 10 and of cargo containers 100 according to the presentdisclosure. As schematically illustrated in FIG. 1, a cargo aerialdelivery system 10 includes a cargo container 100 configured to carryone or more delivery items 20 and a vehicle 200 configured to carrycargo container 100 to each of one or more delivery destinations 22corresponding to delivery item(s) 20. Each delivery item 20 isassociated with a corresponding delivery destination 22, such that cargocontainer 100 and/or cargo aerial delivery system 10 is configured totransport each delivery item 20 to the corresponding deliverydestination 22. Cargo aerial delivery system 10 is configured to receiveinformation for the delivery destination 22 for each delivery item 20via local communication with a secured cargo container 100, such thatcargo aerial delivery system 10 receives destinations for transport ofdelivery items 20 independent of any communication from an externalremotely-located communication network.

Cargo container 100 may be configured to support and/or carry deliveryitem(s) 20 in any appropriate manner. For example, and as schematicallyillustrated in FIG. 1, cargo container 100 may include a container body110 configured to at least partially enclose and support deliveryitem(s) 20 and configured to be selectively and operatively coupled tovehicle 200.

Vehicle 200 may include and/or be any appropriate vehicle, such as anunmanned aerial vehicle (UAV) 200. It is within the scope of the presentdisclosure that cargo container 100 may be configured to be utilized inconjunction with any appropriate vehicle 200, and/or that elementsand/or aspects of cargo aerial delivery systems 10 according to thepresent disclosure may be employed in systems that utilize vehicles 200other than UAVs, such as land-, water-, and/or space-based vehicles.However, without loss of generality, the present disclosure generally isdirected to examples in which vehicle 200 is a UAV. Accordingly,references herein to UAV 200 also may be understood as describing avehicle 200, as appropriate, and vice versa.

In general, and as discussed herein, cargo aerial delivery system 10 isconfigured such that UAV 200 travels to and/or is guided to eachdelivery destination 22 independent of or without UAV 200 receivingdelivery instructions from an external remotely-located communicationnetwork (such as a communication network external to UAV 200 and/orcargo container 100). Instead, and as described herein, cargo container100 is configured to provide information about delivery items 20 anddelivery destinations 22 to UAV 200 to enable and/or direct UAV 200 totravel to each delivery destination 22. In this manner, cargo container100 may be configured to be carried by any of a plurality of unique UAVs200 that are configured to engage cargo container 100.Cargo aerialdelivery system 10 maybe configured such that a given cargo container100 containing delivery item(s) 20 may be operatively coupled to andcarried by any available UAV 200 of a fleet of UAVs 200 for transport ofdelivery items 20 to their destinations without UAV 200 receivingdelivery instructions regarding delivery item(s) 20 other than fromcargo container 100.

As additionally schematically illustrated in FIG. 1, cargo container 100includes a programmable device 120 that stores manifest information 130regarding each delivery item 20. As described in more detail herein,cargo aerial delivery system 10 generally is configured such that UAV200 travels to and/or is guided to each delivery destination 22 based,at least in part, on manifest information 130 (and/or on informationand/or instructions that are derived from manifest information 130).Manifest information 130 may include and/or be any appropriateinformation characterizing delivery item(s) 20 carried by cargocontainer 100. For example, manifest information 130 generally includesan item identifier and item destination information that representsdelivery destination 22 of each delivery item 20. As additionalexamples, manifest information 130 may include item weight informationthat represents a weight of each delivery item 20 for each deliverydestination 22; item identification information that represents anidentity of each delivery item 20; item recipient information thatrepresents an intended recipient of each delivery item 20; hazardousmaterial information that represents a hazardousness associated witheach delivery item 20 (such as may correspond to a safety data sheet(SDS) associated with each delivery item 20); and/or time sensitivityinformation that represents a latest arrival time by which each deliveryitem 20 needs to reach its respective delivery destination 22. However,such examples are not exhaustive, and it is additionally within thescope of the present disclosure that manifest information 130 mayinclude any appropriate additional and/or alternative descriptorscorresponding to delivery item(s) 20.

Cargo aerial delivery system 10, cargo container 100, and/orprogrammable device 120 may be configured to selectively receive, enter,and/or update manifest information 130 in any appropriate manner. Forexample, and as schematically illustrated in FIG. 1, cargo container 100may include an input device 122 configured to enable selectivelyupdating manifest information 130 when a given delivery item 20 is addedto or removed from cargo container 100. Input device 122 may beconfigured to update manifest information 130 in any appropriate manner,such as at least partially automatically and/or at least partiallymanually. As an example, and as schematically illustrated in FIG. 1,input device 122 may include an input scanner 124 configured to scan aportion of delivery item 20 when delivery item 20 is added to or removedfrom cargo container 100, such as via an optical, electrical, and/ormagnetic means. In such examples, input scanner 124 may be manuallyoperated, and/or may be configured to automatically scan delivery item20 as delivery item 20 is added to or removed from cargo container 100.Additionally or alternatively, input device 122 may be configured toreceive a manual input to update manifest information 130, such as via auser interface 126 configured to receive an input from a human user toupdate manifest information 130. In such examples, user interface 126may include and/or be any appropriate interface, such as a keyboard, atouchscreen, and/or a voice-activated control.

As schematically illustrated in FIG. 1, cargo aerial delivery system 10generally includes a delivery system controller 60 configured todetermine and generate an order of delivery, a destination schedule,and/or a delivery itinerary 30 for UAV 200 to travel along to deliverdelivery item(s) 20. For example, when cargo container 100 carries twoor more delivery items 20, delivery itinerary 30 may include and/or bean ordered and/or sequential list of delivery destinations 22corresponding to the two or more delivery items 20.In such examples,delivery itinerary 30 may include and/or be information regarding adelivery sequence in which delivery items 20 are to be delivered to therespective delivery destinations 22. Additionally or alternatively,delivery itinerary 30 may include information regarding a specific routefor UAV 200 to follow, such as speed, altitude, and/or flight pathinformation to direct UAV 200 to delivery destination(s) 22. Deliveryitinerary 30 generally is at least partially based on manifestinformation 130, as described herein.

Delivery system controller 60 may be a component of and/or supported byany appropriate component of cargo aerial delivery system 10. Asexamples, and as schematically illustrated in FIG. 1, cargo container100 and/or UAV 200 may include delivery system controller 60. In anexample in which cargo container 100 includes delivery system controller60, programmable device 120 may be associated with delivery systemcontroller 60. In such examples, programmable device 120 also may bedescribed as generating delivery itinerary 30.

Delivery system controller 60 and/or programmable device 120 may be anysuitable device or devices that are configured to perform the functionsof delivery system controller 60 and/or of programmable device 120discussed herein. For example, the delivery system controller 60 mayinclude one or more of an electronic controller, a dedicated controller,a special-purpose controller, an unmanned aerial vehicle navigationcontroller, a personal computer, a special-purpose computer, or othersuitable controller device. The programmable device 120 may include anRFID device, a display device, a logic device, a memory device, and/or amemory device having non-transitory computer readable media suitable forstoring computer-executable instructions for implementing aspects ofsystems and/or methods according to the present disclosure.

As discussed, when cargo container 100 carries two or more deliveryitems 20, delivery itinerary 30 generally includes information regardingan order and/or sequence in which the delivery items 20 are to bedelivered to the corresponding delivery destinations 22, which is atleast partially based upon manifest information 130 associated withdelivery items 20. In one example, the delivery sequence is arrangedsuch that delivery of a given delivery item 20 is at least partiallyprioritized when the given delivery item 20 has the same deliverydestination 22 and/or the same intended recipient as one or more otherdelivery items. Arranging the delivery sequence in this mannerfacilitates reducing a total weight of delivery items 20 remaining incargo container 100 relatively early in delivery itinerary 30, such asto optimize an energy efficiency of UAV 200. UAV 200 may operate with ahigher energy efficiency when carrying a smaller total weight, such thatremoving weight from cargo container 100 earlier in delivery itinerary30 facilitates operating UAV 200 with a higher energy efficiency for agreater remainder of delivery itinerary 30. Accordingly, deliveryitinerary 30 additionally or alternatively may be configured to at leastpartially prioritize delivering heavier delivery items 20 beforedelivering lighter delivery items 20. For example, manifest information130 may include the weight information regarding each delivery item 20,and delivery itinerary 30 may be at least partially based upon theweight information of delivery items 20 for each delivery destination22. In such examples, the delivery sequence may be arranged at least inpart to prioritize delivering in order of decreasing weight of deliveryitems 20 for each delivery destination 22. As additional examples, thedelivery sequence may be arranged at least in part to prioritizedelivering delivery items 20 in order of decreasing hazardousness (suchas may be represented by the hazardous material informationcorresponding to each delivery item 20) and/or in order of increasinglatest arrival times and/or decreasing time sensitivity (such as may berepresented by the time sensitivity information corresponding to eachdelivery item 20).

Delivery system controller 60 also may be configured to generatedelivery itinerary 30 based on any appropriate considerations, such asto reduce and/or minimize a total travel time required to deliverdelivery items 20, and/or to reduce and/or minimize a total amount ofenergy required to deliver delivery items 20. As an example, deliveryitinerary 30 may be at least partially based on the item destinationinformation. As a more specific example, the delivery sequence may bearranged at least in part to prioritize delivering delivery items 20 inorder of increasing distance from UAV 200 (e.g., relative to an initialposition of UAV 200). Arranging the delivery sequence in this manner maycorrespond to a reduction in a total distance travelled by UAV 200 whilefollowing delivery itinerary 30.

With continued reference to FIG. 1, cargo aerial delivery system 10utilizess a local communication mode 50 configured to convey deliveryinformation 140 from cargo container 100 to UAV 200. As discussed, localcommunication mode 50 generally is configured to convey deliveryinformation 140 from cargo container 100 to UAV 200 independent ofcommunications with an external remotely-located communication network.In this manner, local communication mode 50 enables UAV 200 to transportdelivery items 20 according to delivery itinerary 30 having receiveddelivery itinerary 30, or having generated delivery itinerary 30 uponreceipt of delivery information 140, only from cargo container 100.

As used herein, delivery information 140 generally refers to a set ofinformation that is transferred from cargo container 100 to UAV 200, andgenerally is at least partially based on manifest information 130. Thatis, delivery information 140 may include, be, and/or be based on atleast a portion of manifest information 130. In some examples, deliveryinformation 140 may include and/or be delivery itinerary 30, such as inan example in which cargo container 100 includes delivery systemcontroller 60. That is, in such an example, delivery system controller60 may be configured to generate delivery itinerary 30 at leastpartially based on manifest information 130, such that deliveryitinerary 30 is transferred from cargo container 100 to UAV 200 vialocal communication mode 50. However, this is not required of allexamples of cargo aerial delivery system 10, and it additionally iswithin the scope of the present disclosure that delivery itinerary 30may be generated subsequent to conveying delivery information 140 vialocal communication mode 50 from cargo container 100 to UAV 200. As anexample, in an example in which UAV 200 includes delivery systemcontroller 60, delivery system controller 60 may be configured togenerate delivery itinerary 30 based on delivery information 140 andsubsequent to conveying delivery information 140 via local communicationmode 50 from cargo container 100 to UAV 200.

Local communication mode 50 may include and/or be any appropriate systemfor conveying delivery information 140 from cargo container 100 to UAV200. As an example, and as schematically illustrated in FIG. 1, cargocontainer 100 may include a container communication device 150 (such asmay be supported by container body 110) and UAV 200 may include avehicle communication device 250 where the local communication mode 50is utilized by the container communication device 150 and vehiclecommunication device 250. In such examples, the local communication mode50 generally is utilized to convey delivery information 140 fromcontainer communication device 150 to vehicle communication device 250.Examples of a local communication mode 50 may include near-fieldcommunication, Bluetooth communication, RF communication and/or an RFIDreader, a bar code scanner or other code scanner, or other suitablemodes of local communication, where information may be conveyed via anelectromagnetic signal, an electrical signal, an optical signal, a radiofrequency signal, a near-field communication signal, a wirelessconnection, a wired connection, a direct connection, and/or a visualconnection. In such examples, communication of delivery information 140from container communication device 150 to vehicle communication device250 may be initiated in any appropriate manner. As examples, containercommunication device 150 may be configured to initiate communication ofdelivery information 140 to vehicle communication device 250, or may beconfigured to convey delivery information 140 to vehicle communicationdevice 250 responsive to receiving a request for delivery information140 from vehicle communication device 250.

Delivery information 140 may be conveyed from container communicationdevice 150 to vehicle communication device 250 in any appropriate mannerand/or in any appropriate form, such as via an electromagnetic signal,an electrical signal, an optical signal, a radio frequency signal, anear-field communication signal, a wireless connection, a wiredconnection, a direct connection, and/or a visual connection. As anexample, container communication device 150 may be configured tocomplete an electrical connection with vehicle communication device 250when container body 110 is operatively coupled to UAV 200. Additionallyor alternatively, container communication device 150 may be configuredto actively transmit delivery information 140 to vehicle communicationdevice 250. For example, and as schematically illustrated in FIG. 1,container communication device 150 may include a wireless transmitter152 configured to wirelessly transmit delivery information 140 tovehicle communication device 250. In other examples, containercommunication device 150 may be configured to passively provide deliveryinformation 140 to vehicle communication device 250. As more specificexamples of such passive communication, container communication device150 may include and/or be a barcode, a matrix barcode, a magneticstripe, a radio frequency identification (RFID) tag, and/or a near-fieldcommunication (NFC) tag, and vehicle communication device 250 may beconfigured to read, scan, and/or otherwise receive delivery information140 from container communication device 150.

UAV 200 may be configured to receive and/or engage cargo container 100in any appropriate manner. For example, and as schematically illustratedin FIG. 1, UAV 200 may include a docking bay 210 such that cargocontainer 100 is at least partially received within docking bay 210 whencargo container 100 is operatively coupled to UAV 200. In such examples,docking bay 210 may refer to a portion of UAV 200 that is at leastpartially enclosed, such as to at least partially encapsulate cargocontainer 100. However, this is not required of all examples, and itadditionally is within the scope of the present disclosure that dockingbay 210 may refer to a portion of UAV 200 that is at least partiallyexposed to an exterior environment. Additionally or alternatively, UAV200 may include a cargo container receiver 212 configured to selectivelyand operatively engage cargo container 100 such that cargo container 100is secured to UAV 200 and such that UAV 200 may carry cargo container100. In such examples, cargo container 100 may be described as includinga vehicle engagement structure 160 configured to selectively andoperatively engage cargo container receiver 212 to operatively securecargo container 100 to UAV 200. Equivalently, cargo container receiver212 may be described as being configured to selectively and operativelyengage vehicle engagement structure 160 to operatively secure cargocontainer 100 to UAV 200. In this manner, one or both of vehicleengagement structure 160 and cargo container receiver 212 may include astructure that is mechanically actuated, examples of which may include alatch, a hook, a clamp, a cradle, etc. Additionally or alternatively,vehicle engagement structure 160 may refer to a substantially staticportion of cargo container 100 that is engaged by cargo containerreceiver 212, and/or cargo container receiver 212 may refer to asubstantially static portion of UAV 200 that is engaged by vehicleengagement structure 160. In such examples, cargo container 100 may bedescribed as being configured to be selectively transitioned between adocked configuration, in which cargo container receiver 212 operativelyengages cargo container 100 and/or vehicle engagement structure 160 suchthat UAV 200 may carry cargo container 100, and an undockedconfiguration, in which cargo container 100 is removed from UAV 200.

Vehicle engagement structure 160 and/or cargo container receiver 212 mayinclude and/or be any appropriate portions of cargo container 100 and/orUAV 200. As examples, vehicle engagement structure 160 may include astructure that extends from container body 110 to meet UAV 200 and/orcargo container receiver 212, or may simply be a portion of cargocontainer 100 and/or of container body 110 that engages (and/or that isengaged by) cargo container receiver 212. Similarly, cargo containerreceiver 212 may include a structure that extends within docking bay 210to meet cargo container 100 and/or vehicle engagement structure 160, ormay simply be a portion of UAV 200 and/or of docking bay 210 thatengages (and/or that is engaged by) vehicle engagement structure 160.

Vehicle engagement structure 160 and/or cargo container receiver 212 maybe at least partially load-bearing, and/or may be configured such thatengagement between vehicle engagement structure 160 and cargo containerreceiver 212 is at least partially load-bearing. Vehicle engagementstructure 160 and/or cargo container receiver 212 may be configured toat least partially restrict cargo container 100 from transitioning fromthe docked configuration to the undocked configuration, and/or may beconfigured to at least partially support a weight of cargo container100. That is, vehicle engagement structure 160 and/or cargo containerreceiver 212 may be configured such that cargo container receiver 212 atleast partially supports the weight of cargo container 100 when vehicleengagement structure 160 operatively engages cargo container receiver212 and/or when UAV 200 carries cargo container 100. Additionally oralternatively, vehicle engagement structure 160 and/or cargo containerreceiver 212 may be configured such that cargo container 100 and/orvehicle engagement structure 160 at least partially supports a weight ofUAV 200 when vehicle engagement structure 160 operatively engages cargocontainer receiver 212. For example, cargo container 100 may beconfigured to contact a ground surface when UAV 200 is not in flight andwhen cargo container 100 is operatively secured to UAV 200 such thatcargo container 100 supports UAV 200, such as to support UAV 200 abovethe ground surface. In such examples, cargo container 100 may include alanding gear, a landing skid, a ground-contacting surface, and/or anyother appropriate component for engaging the ground surface. In examplesin which vehicle engagement structure 160 and/or cargo containerreceiver 212 is at least partially load-bearing, vehicle engagementstructure 160 and/or cargo container receiver 212 also may be describedas representing a detachable load-bearing structure.

Vehicle engagement structure 160 and/or cargo container receiver 212additionally or alternatively may be configured such that cargocontainer 100 is restricted from transitioning from the undockedconfiguration to the docked configuration unless vehicle engagementstructure 160 and cargo container receiver 212 are aligned and/orotherwise in a predetermined orientation relative to one another. Insuch examples, vehicle engagement structure 160 and/or cargo containerreceiver 212 may be described as being keyed. In some examples, vehicleengagement structure 160 may include container communication device 150,such as to permit an electrical connection between containercommunication device 150 and vehicle communication device 250 whencontainer body 110 is operatively coupled to UAV 200.

When present, vehicle engagement structure 160 generally is configuredto selectively and operatively engage cargo container receiver 212 tosecure cargo container 100 to UAV 200 when cargo container 100 and/orcontainer body 110 is operatively coupled to UAV 200. For example,vehicle engagement structure 160 may be configured to mechanicallyengage container body 110 and/or cargo container receiver 212 such thatcargo container 100 is at least partially restricted from movingrelative to UAV 200 when cargo container 100 and/or container body 110is operatively coupled to UAV 200 and when UAV 200 carries cargocontainer 100. To ensure and/or facilitate operative coupling betweenvehicle engagement structure 160 and cargo container receiver 212,vehicle engagement structure 160 may be configured to operatively engagecargo container receiver 212 only when container body 110 is in apredetermined orientation relative to UAV 200 and/or docking bay 210.

Cargo container 100 and/or UAV 200 may include one or more componentsconfigured to detect when container body 110 is operatively coupled toUAV 200. For example, and as schematically illustrated in FIG. 1, cargocontainer 100 and/or UAV 200 may include a cargo container engagementsensor 214 configured to detect when container body 110 is operativelycoupled to UAV 200 and/or when cargo container 100 is in the dockedconfiguration. Cargo container engagement sensor 214 may include and/orbe any appropriate mechanism, and may be a component of any appropriateportion of cargo aerial delivery system 10. As examples, cargo container100, vehicle engagement structure 160, UAV 200, and/or cargo containerreceiver 212 may include cargo container engagement sensor 214.

In examples of cargo aerial delivery system 10 that include cargocontainer engagement sensor 214, local communication mode 50 may beutilized to convey delivery information 140 from cargo container 100 toUAV 200 based, at least in part, on cargo container engagement sensor214 indicating that container body 110 is operatively coupled to UAV200. For example, container communication device 150 may be configuredto convey delivery information 140 to vehicle communication device 250responsive to cargo container engagement sensor 214 indicating thatcontainer body 110 is operatively coupled to UAV 200.Local communicationsystem 50 may be configured to initiate a transfer of deliveryinformation 140 from container communication device 150 to vehiclecommunication device 250 responsive to cargo container engagement sensor214 indicating that cargo container 100 is in the docked configuration.Additionally or alternatively, delivery system controller 60 and/orprogrammable device 120 may be configured to generate delivery itinerary30, and/or to convey delivery itinerary 30 and/or delivery information140 to UAV 200, responsive to cargo container engagement sensor 214indicating that vehicle engagement structure 160 operatively engagescargo container receiver 212.

As discussed, as used herein, UAV 200 represents an exemplary,non-exclusive embodiment of vehicle 200 for carrying cargo container100. In such examples, UAV 200 may be any appropriate aerial vehicle forcarrying cargo container 100. For example, and as schematicallyillustrated in FIG. 1, UAV 200 may be a rotorcraft that includes one ormore rotors 230. As more specific examples, UAV 200 may include onerotor 230, two rotors 230, three rotors 230, four rotors 230, or morethan four rotors 230. In such examples, rotor(s) 230 may be at leastpartially battery-powered. Accordingly, in contrast to an example ofvehicle 200 that consumes a fuel while traveling, UAV 200 in the form ofa battery-powered rotorcraft may experience a decrease in total carriedweight only upon unloading delivery items 20 at respective deliverydestinations 22. In this manner, configuring delivery itinerary 30 toprioritize delivering delivery items 20 in order of decreasing weightmay be particularly advantageous in examples in which UAV 200 isbattery-powered.

Cargo container 100 may have any appropriate specifications and/ordimensions for carrying delivery item(s) 20. As examples, container body110 of cargo container 100 may define a volume that has a capacity thatis at least 10 liters (L), at least 50 L, at least 100 L, at least 500L, at least 1,000 L, at least 5,000 L, at least 10,000 L, at least50,000 L, at most 100,000 L, at most 70,000 L, at most 20,000 L, at most7,000 L, at most 2,000 L, at most 700 L, at most 200 L, at most 70 L,and/or at most 20 L.

Additionally or alternatively, cargo container 100 and delivery item(s)contained therein collectively may have a total mass that is at least 1kilogram (kg), at least 5 kg, at least 10 kg, at least 50 kg, at least100 kg, at least 500 kg, at least 1,000 kg, at most 1,500 kg, at most700 kg, at most 200 kg, at most 70 kg, at most 20 kg, at most 7 kg,and/or at most 2 kg.

FIG. 2 schematically illustrates an example of a delivery route 32 thatmay be followed by UAV 200, such as may correspond to delivery itinerary30. Delivery route 32 may correspond to and/or be a spatial and/ortemporal path followed by UAV 200 as UAV 200 follows and/or proceedsaccording to delivery itinerary 30, and/or may include and/or be asequence of delivery destinations 22 specified by delivery itinerary30.As used herein, delivery itinerary 30 generally refers to a set ofinformation and/or instructions corresponding to a route to be followedby UAV 200, while delivery route 32 generally refers to the route itself(as expressed in any appropriate manner). In particular, FIG. 2schematically illustrates an example of delivery route 32 that is basedupon delivery itinerary 30 in which the delivery sequence is at leastpartially based upon a consideration other than distance between UAV 200and delivery destination 22. As further schematically illustrated inFIG. 2, cargo aerial delivery system 10 additionally may include aground-based control system 12 configured to monitor UAV 200 as UAV 200travels along delivery route 32. In such examples, and as schematicallyillustrated in FIGS. 1-2, UAV 200 additionally may include a groundcommunication device 220 configured to communicate with ground-basedcontrol system 12. In this manner, ground-based control system 12 may beconfigured to monitor a location of UAV 200 and/or a delivery status ofdelivery item(s) carried by UAV 200 as UAV 200 travels along deliveryroute 32. As discussed, ground-based control system 12 generally is notconfigured to provide UAV 200 with manifest information 130, deliveryinformation 140, or delivery itinerary 30 prior to UAV 200 embarkingupon delivery route 32.As discussed herein, ground-based control system12 does not include and/or represent an external remotely locatedcommunication network that conveys delivery information 140 to UAV 200.

FIGS. 3-5 provide less schematic illustrations of a portion of anexample of cargo aerial delivery system 10. More specifically, FIGS. 3-5illustrate an example of cargo aerial delivery system 10 in which UAV200 is a rotorcraft with four rotors 230 and in which cargo container100 is fully contained within docking bay 210 of UAV 200 when in thedocked configuration. FIGS. 3 and 5 illustrate examples in which cargocontainer 100 is removed from UAV 200 (and hence is in the undockedconfiguration), while FIG. 4 illustrates an example in which cargocontainer 100 is operatively received within (and fully enclosed within)docking bay 210, such that cargo container 100 is concealed from view.As seen in FIGS. 3 and 5, FIGS. 3-5 illustrate an example in which cargocontainer 100 includes vehicle engagement structure 160 (shown in FIG.3) and in which UAV 200 includes cargo container receiver 212 such thatvehicle engagement structure 160 and cargo container receiver 212 engageone another when cargo container 100 is in the docked configuration.Additionally, in the example of FIGS. 3-5, cargo container receiver 212includes cargo container engagement sensor 214 (as seen in FIG. 5).

FIG. 6 is a flowchart schematically depicting methods 300, according tothe present disclosure, of utilizing a cargo aerial delivery system(such as cargo aerial delivery system 10) that includes a cargocontainer (such as cargo container 100) and a UAV (such as UAV 200) todeliver one or more delivery items (such as delivery items 20) torespective delivery destinations (such as delivery destinations 22). InFIG. 6, some steps are illustrated in dashed boxes indicating that suchsteps may be optional or may correspond to an optional version of amethod according to the present disclosure. That said, not all methodsaccording to the present disclosure are required to include the stepsillustrated in solid boxes. The methods and steps illustrated in FIG. 6are not limiting and other methods and steps are within the scope of thepresent disclosure, including methods having greater than or fewer thanthe number of steps illustrated, as understood from the discussionsherein.

As shown in FIG. 6, methods 300 include loading, at 310, the deliveryitem(s) into a container body (such as container body 110) of the cargocontainer and entering, at 320, manifest information (such as manifestinformation 130) regarding each delivery item into a programmable device(such as programmable device 120) of the cargo container. The enteringthe manifest information at 320 may be performed in any appropriatemanner, such as by scanning each delivery item with an input scanner(such as input scanner 124) and/or by manually entering the manifestinformation via a user interface (such as user interface 126). Methods300 additionally include operatively engaging, at 330, the cargocontainer with the UAV; generating, at 350, a delivery itinerary (suchas delivery itinerary 30) for delivering the delivery item(s) to therespective delivery destination(s); transporting, at 360, the cargocontainer with the UAV along the delivery itinerary; and unloading, at370, each delivery item at the respective delivery destination.

The engaging the cargo container with the UAV at 330 may be performed inany appropriate manner. As an example, the engaging at 330 may includeengaging the cargo container with a cargo container receiver (such ascargo container receiver 212) of the UAV to transition the cargocontainer from an undocked configuration to a docked configuration. Asanother example, the engaging at 330 may include forming an electricalconnection between a vehicle communication device (such as vehiclecommunication device 250) and a container communication device (such ascontainer communication device 150). Additionally or alternatively, andas shown in FIG. 6, the engaging at 330 may include generating andtransmitting, at 332, an engagement signal with a cargo containerengagement sensor (such as cargo container engagement sensor 214)indicating that the cargo container is in the docked configuration. Insuch examples, the generating and transmitting at 332 may includetransmitting the engagement signal to the container communication deviceand/or to the vehicle communication device.

As additionally shown in FIG. 6, methods 300 further may include,subsequent to the entering the manifest information at 320,transferring, at 340, delivery information (such as delivery information140) from the cargo container to the UAV. In such examples, and asdiscussed herein, the delivery information is at least partially basedon the manifest information. The transferring at 340 may be performed inany appropriate manner and/or between any appropriate components of thecargo aerial delivery system. For example, the transferring at 340 mayinclude transferring the delivery information from the containercommunication device to the vehicle communication device. In suchexamples, the transferring at 340 may be performed via a wiredconnection and/or via a wireless connection between the containercommunication device and the vehicle communication device. Additionallyor alternatively, in an example in which methods 300 include thegenerating and transmitting the engagement signal at 332, thetransferring at 340 may be performed responsive to the cargo containerengagement sensor indicating that the cargo container is in the dockedconfiguration. For example, in an example in which the generating andtransmitting at 332 includes transmitting the engagement signal to thecontainer communication device, the container communication device mayinitiate the transferring the delivery information at 340 upon receiptof the engagement signal. Similarly, in an example in which thegenerating and transmitting at 332 includes transmitting the engagementsignal to the vehicle communication device, the vehicle communicationdevice may initiate the transferring the delivery information at 320upon receipt of the engagement signal.

As discussed herein, the generating the delivery itinerary at 350generally is at least partially based on the manifest information, andmay be performed by a delivery system controller (such as deliverysystem controller 60). As an example, the UAV may include the deliverysystem controller, and the generating the delivery itinerary at 350 maybe performed subsequent to the transferring the delivery information at340. Additionally or alternatively, the generating the deliveryitinerary at 350 may be performed subsequent to the generating andtransmitting the engagement signal at 332.

As further shown in FIG. 6, the generating the delivery itinerary at 350may include calculating, at 352, an optimal delivery route (such asdelivery route 32 and/or such as may otherwise correspond to thedelivery itinerary). The calculating the optimal delivery route at 352may be performed in any appropriate manner and/or based on anyappropriate considerations. As an example, and as shown in FIG. 6, thecalculating the optimal delivery route at 352 may include calculating,at 354, a priority score associated with each delivery item such thatthe generating the delivery itinerary at 350 includes configuring thedelivery itinerary to deliver the delivery items in order of descendingpriority score.

The calculating the priority scores at 354 may be based upon anyappropriate considerations and/or properties of the delivery items. Forexample, and as discussed, it may be desirable to prioritize deliveringdelivery items that are relatively heavy and/or that share a deliverydestination with other delivery items, such as to reduce a total weightof the delivery items carried by the UAV. Accordingly, the priorityscore of a given delivery item may be at least partially based upon itemweight information corresponding to the given delivery item. Forexample, the priority score of the given delivery item may be positivelycorrelated with the weight of the given delivery item.

Additionally or alternatively, the priority score of a given deliveryitem may be at least partially based upon hazardous material informationcorresponding to the given delivery item. For example, the priorityscore of the given delivery item may be positively correlated with thehazardousness of the given delivery item.

Additionally or alternatively, the priority score of a given deliveryitem may be at least partially based upon item destination informationcorresponding to the given delivery item. For example, the priorityscore of the given delivery item maybe negatively correlated with adistance between the UAV and the delivery destination of the givendelivery item. As another example, the priority score of the givendelivery item may be positively correlated with the number of otherdelivery items that have the same delivery destination as the givendelivery item.

Additionally or alternatively, the priority score of the given deliveryitem may be at least partially based upon time sensitivity informationcorresponding to the given delivery item. For example, the priorityscore of the given delivery item may be negatively correlated with atime interval between a present time and a latest arrival time by whichthe given delivery item needs to reach the respective deliverydestination.

Additionally or alternatively, the priority score of a given deliveryitem may be at least partially based upon item recipient informationcorresponding to the given delivery item. For example, the priorityscore of the given delivery item may be positively correlated with thenumber of other delivery items that have the same intended recipient asthe given delivery item.

Illustrative, non-exclusive examples of inventive subject matteraccording to the present disclosure are described in the followingenumerated paragraphs:

A1. A cargo container (100) for carrying one or more delivery items (20)to respective delivery destinations (22), the cargo container (100)comprising:

a container body (110) configured to at least partially enclose andsupport the one or more delivery items (20) and configured to beselectively and operatively coupled to a vehicle (200);

a programmable device (120) supported by the container body (110) thatstores manifest information (130) regarding each delivery item (20) ofthe one or more delivery items (20); and

a container communication device (150) supported by the container body(110) and configured to convey delivery information (140) to a vehiclecommunication device (250) of the vehicle (200) to direct the vehicle tothe respective delivery destinations (22) of the one or more deliveryitems (20);

wherein the manifest information (130) includes item destinationinformation that represents a delivery destination (22) of each deliveryitem (20) of the one or more delivery items (20); and wherein thedelivery information (140) is based, at least in part, on the itemdestination information.

A2. The cargo container (100) of paragraph A1, wherein the deliveryinformation (140) includes at least a portion of the manifestinformation (130).

A3. The cargo container (100) of any of paragraphs A1-A2, wherein thecontainer body (110) defines a volume that has a capacity that is one ormore or at least 10 liters (L), at least 50 L, at least 100 L, at least500 L, at least 1,000 L, at least 5,000 L, at least 10,000 L, at least50,000 L, at most 100,000 L, at most 70,000 L, at most 20,000 L, at most7,000 L, at most 2,000 L, at most 700 L, at most 200 L, at most 70 L, orat most 20 L.

A4. The cargo container (100) of any of paragraphs A1-A3, wherein thecargo container (100) is configured to be operatively carried by any ofa plurality of unique vehicles (200) that are configured to engage thecargo container (100).

A5. The cargo container (100) of any of paragraphs A1-A4, furthercomprising an input device (122) configured to enable selectivelyupdating the manifest information (130) when a given delivery item (20)of the one or more delivery items (20) is added to or removed from thecargo container (100).

A6. The cargo container (100) of paragraph A5, wherein the input device(122) is configured to automatically update the manifest information(130) when the given delivery item (20) is added to or removed from thecargo container (100).

A7. The cargo container (100) of any of paragraphs A5-A6, wherein theinput device (122) includes an input scanner (124) configured to scan aportion of the given delivery item (20) when the given delivery item(20) is added to or removed from the cargo container (100).

A8. The cargo container (100) of paragraph A7, wherein the input device(122) is configured to receive a manual input to update the manifestinformation (130).

A9. The cargo container (100) of paragraph A8, wherein the input device(122) includes a user interface (126) configured to receive an inputfrom a human user to update the manifest information (130).

A10. The cargo container (100) of any of paragraphs A1-A9, wherein thevehicle (200) is an unmanned aerial vehicle (UAV) (200).

A11. The cargo container (100) of any of paragraphs A1-A10, furthercomprising a vehicle engagement structure (160) configured toselectively and operatively engage a cargo container receiver (212) ofthe vehicle (200) to secure the cargo container (100) to the vehicle(200) when the container body (110) is operatively coupled to thevehicle (200).

A12. The cargo container (100) of paragraph A11, wherein the vehicleengagement structure (160) is configured to mechanically engage thecargo container receiver (212) such that the cargo container (100) is atleast partially restricted from moving relative to the vehicle (200)when the container body (110) is operatively coupled to the vehicle(200) and when the vehicle (200) carries the cargo container (100).

A13. The cargo container (100) of any of paragraphs A11-A12, wherein thevehicle engagement structure (160) is configured to operatively engagethe cargo container receiver (212) only when the container body (110) isin a predetermined orientation relative to the vehicle (200).

A14. The cargo container (100) of any of paragraphs A11-A13, wherein oneor both of the vehicle engagement structure (160) and the cargocontainer receiver (212) is at least partially load-bearing when thevehicle engagement structure (160) operatively engages the cargocontainer receiver (212).

A15. The cargo container (100) of paragraph A14, wherein the cargocontainer receiver (212) is configured to at least partially support aweight of the cargo container (100) when the vehicle engagementstructure (160) operatively engages the cargo container receiver (212)and when the vehicle (200) carries the cargo container (100).

A16. The cargo container (100) of any of paragraphs A14-A15, wherein thevehicle engagement structure (160) is configured to at least partiallysupport a weight of the vehicle (200) when the vehicle engagementstructure (160) operatively engages the cargo container receiver (212)and when the cargo container (100) rests upon a ground surface.

A17. The cargo container (100) of paragraph A16, wherein the cargocontainer (100) is configured to support the vehicle (200) above theground surface when the vehicle engagement structure (160) operativelyengages the cargo container receiver (212) and when the cargo container(100) rests upon the ground surface.

A18. The cargo container (100) of any of paragraphs A1-A17, wherein thecargo container (100) includes one or more of a landing gear, a landingskid, or a ground-contacting surface configured to engage the groundsurface.

A19. The cargo container (100) of any of paragraphs A1-A18, wherein oneor both of the vehicle (200) and the cargo container (100) includes acargo container engagement sensor (214) configured to detect when thecontainer body (110) is operatively coupled to the vehicle (200).

A20. The cargo container (100) of paragraph A19, wherein the containercommunication device (150) is configured to convey the deliveryinformation (140) to the vehicle communication device (250) responsiveto the cargo container engagement sensor (214) indicating that thecontainer body (110) is operatively coupled to the vehicle (200).

A21. The cargo container (100) of any of paragraphs A1-A20, wherein thecontainer communication device (150) is configured to convey thedelivery information (140) to the vehicle communication device (250)independent of communications with an external remotely locatedcommunication network.

A22. The cargo container (100) of any of paragraphs A1-A21, wherein thecontainer communication device (150) is configured to initiatecommunication of the delivery information (140) to the vehiclecommunication device (250).

A23. The cargo container (100) of any of paragraphs A1-A22, wherein thecontainer communication device (150) is configured to convey thedelivery information (140) to the vehicle communication device (250)responsive to receiving a request for the delivery information (140)from the vehicle communication device (250).

A24. The cargo container (100) of any of paragraphs A1-A23, wherein thecontainer communication device (150) is configured to actively transmitthe delivery information (140) to the vehicle communication device(250).

A25. The cargo container (100) of any of paragraphs A1-A24, wherein thecontainer communication device (150) is configured to form an electricalconnection with the vehicle communication device (250) when thecontainer body (110) is operatively coupled to the vehicle (200).

A26. The cargo container (100) of any of paragraphs A1-A25, whereina/the vehicle engagement structure (160) includes the containercommunication device (150).

A27. The cargo container (100) of any of paragraphs A1-A26, wherein thecontainer communication device (150) includes a wireless transmitter(152) configured to wirelessly transmit the delivery information (140)to the vehicle communication device (250).

A28. The cargo container (100) of any of paragraphs A1-A27, wherein thecontainer communication device (150) is configured to passively providethe delivery information (140) to the vehicle communication device(250).

A29. The cargo container (100) of paragraph A28, wherein the containercommunication device (150) includes one or more of a barcode, a matrixbarcode, a magnetic stripe, a radio frequency identification (RFID) tag,or a near-field communication (NFC) tag.

A30. The cargo container (100) of any of paragraphs A1-A29, wherein theone or more delivery items (20) include two or more delivery items (20),and wherein the delivery information (140) includes a delivery itinerary(30) that includes information regarding a delivery sequence in whichthe two or more delivery items (20) are to be delivered to therespective delivery destinations (22).

A31. The cargo container (100) of paragraph A30, wherein theprogrammable device (120) is configured to generate the deliveryitinerary (30) based, at least in part, upon the manifest information(130).

A32. The cargo container (100) of any of paragraphs A30-A31, wherein theprogrammable device (120) is configured to generate the deliveryitinerary (30) responsive to a/the cargo container engagement sensor(214) indicating that a/the vehicle engagement structure (160)operatively engages a/the cargo container receiver (212).

A33. The cargo container (100) of any of paragraphs A30-A32, wherein theprogrammable device (120) is configured to convey the delivery itinerary(30) to the vehicle (200) responsive to a/the cargo container engagementsensor (214) indicating that a/the vehicle engagement structure (160)operatively engages a/the cargo container receiver (212).

A34. The cargo container (100) of any of paragraphs A30-A33, wherein thedelivery itinerary (30) is based, at least in part, on the itemdestination information.

A35. The cargo container (100) of paragraph A34, wherein the deliverysequence is arranged at least in part to prioritize delivering the twoor more delivery items (20) in order of increasing distance from thevehicle (200).

A36. The cargo container (100) of any of paragraphs A34-A35, wherein thedelivery sequence is arranged such that delivery of a given deliveryitem (20) of the two or more delivery items (20) is at least partiallyprioritized when the given delivery item (20) has the same deliverydestination (22) as one or more other delivery items (20) of the two ormore delivery items (20).

A37. The cargo container (100) of any of paragraphs A30-A36, wherein themanifest information (130) includes item weight information thatrepresents a weight of each of the two or more delivery items (20), andwherein the delivery itinerary (30) is based, at least in part, on theitem weight information.

A38. The cargo container (100) of paragraph A37, wherein the deliverysequence is arranged at least in part to prioritize delivering the twoor more delivery items (20) in order of decreasing weight of the two ormore delivery items (20) for each respective delivery destination (22).

A39. The cargo container (100) of any of paragraphs A30-A38, wherein themanifest information (130) further includes item recipient informationthat represents an intended recipient of each of the two or moredelivery items (20).

A40. The cargo container (100) of paragraph A39, wherein the deliverysequence is arranged such that delivery of a given delivery item (20) ofthe two or more delivery items (20) is at least partially prioritizedwhen the given delivery item (20) has the same intended recipient as oneor more other delivery items (20) of the two or more delivery items(20).

A41. The cargo container (100) of any of paragraphs A30-A40, wherein themanifest information (130) further includes hazardous materialinformation that represents a hazardousness associated with each of thetwo or more delivery items (20).

A42. The cargo container (100) of paragraph A41, wherein the deliverysequence is arranged at least in part to prioritize delivering the twoor more delivery items (20) in order of decreasing hazardousness.

A43. The cargo container (100) of any of paragraphs A30-A42, wherein themanifest information (130) further includes time sensitivity informationthat represents a latest arrival time by which each of the two or moredelivery items (20) needs to reach the respective delivery destinations(22).

A44. The cargo container (100) of paragraph A43, wherein the deliverysequence is arranged at least in part to prioritize delivering the twoor more delivery items (20) in order of increasing latest arrival times.

B1. A cargo aerial delivery system (10) for delivering one or moredelivery items (20) to one or more delivery destinations (22), the cargoaerial delivery system (10) comprising:

a cargo container (100) configured to carry the one or more deliveryitems (20); and

an unmanned aerial vehicle (UAV) (200) configured to carry the cargocontainer (100) to each of one or more delivery destinations (22)corresponding to the one or more delivery items (20);

wherein the cargo container (100) includes a programmable device (120)that stores manifest information (130) regarding each delivery item (20)of the one or more delivery items (20); wherein the manifest information(130) includes item destination information that represents therespective delivery destination (22) of each delivery item (20) of theone or more delivery items (20); wherein the cargo aerial deliverysystem (10) further utilizes a local communication mode (50) configuredto convey delivery information (140) from the cargo container (100) tothe UAV (200), and wherein the delivery information (140) is based, atleast in part, on the item destination information.

B2. The cargo aerial delivery system (10) of paragraph B1, wherein thecargo container (100) is the cargo container (100) of any of paragraphsA1-A44.

B3. The cargo aerial delivery system (10) of any of paragraphs B1-B2,wherein the cargo container (100) is configured to be carried by any ofa plurality of unique UAVs (200) that are configured to engage the cargocontainer (100).

B4. The cargo aerial delivery system (10) of any of paragraphs B1-B3,wherein the manifest information (130) further includes a/the itemweight information that represents a/the weight of each delivery item(20) of the one or more delivery items (20).

B5. The cargo aerial delivery system (10) of any of paragraphs B1-B4,wherein the manifest information (130) further includes a/the itemidentification information that represents an/the identity of eachdelivery item (20) of the one or more delivery items (20).

B6. The cargo aerial delivery system (10) of any of paragraphs B1-B5,wherein the manifest information (130) further includes a/the itemrecipient information that represents an/the intended recipient of eachdelivery item (20) of the one or more delivery items (20).

B7. The cargo aerial delivery system (10) of any of paragraphs B1-B6,wherein the manifest information (130) further includes a/the hazardousmaterial information that represents a/the hazardousness associated witheach delivery item (20) of the one or more delivery items (20).

B8. The cargo aerial delivery system (10) of paragraph B7, wherein thehazardous material information corresponds to a safety data sheet (SDS)associated with each delivery item (20) of the one or more deliveryitems (20).

B9. The cargo aerial delivery system (10) of any of paragraphs B1-B8,wherein the manifest information (130) further includes a/the timesensitivity information that represents a/the latest arrival time bywhich each delivery item (20) of the one or more delivery items (20)needs to reach the respective delivery destination (22).

B10. The cargo aerial delivery system (10) of any of paragraphs B1-B9,wherein the UAV (200) includes a docking bay (210), and wherein thecargo container (100) is at least partially received within the dockingbay (210) when the cargo container (100) is operatively coupled to theUAV (200).

B11. The cargo aerial delivery system (10) of any of paragraphs B1-B10,wherein the cargo container (100) and the one or more delivery items(20) collectively have a total mass that is one or more of at least 1kilogram (kg), at least 5 kg, at least 10 kg, at least 50 kg, at least100 kg, at least 500 kg, at least 1,000 kg, at most 1,500 kg, at most700 kg, at most 200 kg, at most 70 kg, at most 20 kg, at most 7 kg, orat most 2 kg.

B12. The cargo aerial delivery system (10) of any of paragraphs B1-B11,wherein the UAV (200) is a rotorcraft with one or more rotors (230).

B13. The cargo aerial delivery system (10) of paragraph B12, wherein theone or more rotors (230) includes one rotor (230), two rotors (230),three rotors (230), four rotors (230), or more than four rotors (230).

B14. The cargo aerial delivery system (10) of any of paragraphs B12-B13,wherein the one or more rotors (230) are at least partiallybattery-powered.

B15. The cargo aerial delivery system (10) of any of paragraphs B1-B14,wherein the local communication mode (50) is utilized to convey thedelivery information (140) from the cargo container (100) directly tothe UAV (200).

B16. The cargo aerial delivery system (10) of any of paragraphs B1-B15,wherein the local communication mode (50) is utilizes to convey thedelivery information (140) from the cargo container (100) to the UAV(200) independent of communications with an external remotely-locatedcommunication network.

B17. The cargo aerial delivery system (10) of any of paragraphs B1-B16,wherein the UAV (200) includes a vehicle communication device (250),wherein the cargo container (100) includes a container communicationdevice (150), and wherein the local communication mode (50) is utilizedby the vehicle communication device (250) and the containercommunication device (150).

B18. The cargo aerial delivery system (10) of paragraph B17, wherein thelocal communication mode (50) is utilized to convey the deliveryinformation (140) from the container communication device (150) to thevehicle communication device (250) via one or more of near-fieldcommunication, Bluetooth communication, radio frequency (RF)communication, a code scanner, a bar code scanner, an electromagneticsignal, an electrical signal, an optical signal, an RF signal, anear-field communication signal, a wireless connection, a wiredconnection, a direct connection, or a visual connection.

B19. The cargo aerial delivery system (10) of any of paragraphs B1-B18,further comprising a delivery system controller (60) configured togenerate a/the delivery itinerary (30) for the UAV (200) to travel alongto deliver the one or more delivery items (20), wherein the deliveryitinerary (30) is based, at least in part, on the manifest information(130).

B20. The cargo aerial delivery system (10) of paragraph B19, wherein thedelivery information (140) includes, and optionally is, the deliveryitinerary (30).

B21. The cargo aerial delivery system (10) of any of paragraphs B19-B20,wherein the UAV (200) includes the delivery system controller (60).

B22. The cargo aerial delivery system (10) of any of paragraphs B19-B21,wherein the cargo container (100) includes the delivery systemcontroller (60).

B23. The cargo aerial delivery system (10) of paragraph B22, wherein theprogrammable device (120) includes the delivery system controller (60).

B24. The cargo aerial delivery system (10) of any of paragraphs B19-B23,wherein the delivery system controller (60) is configured to generatethe delivery itinerary (30) based, at least in part, on a/the itemweight information regarding each delivery item (20) of the one or moredelivery items (20) for each delivery destination (22).

B25. The cargo aerial delivery system (10) of paragraph B24, wherein theone or more delivery items (20) include two or more delivery items (20),and wherein the delivery system controller (60) is configured togenerate the delivery itinerary (30) such that the two or more deliveryitems (20) are delivered to the respective delivery destinations (22) atleast partially in order of descending weight of the two or moredelivery items (20) for each delivery destination (22).

B26. The cargo aerial delivery system (10) of any of paragraphs B9-B25,wherein the delivery system controller (60) is configured to generatethe delivery itinerary (30) based, at least in part, on a/the hazardousmaterial information regarding each delivery item (20) of the one ormore delivery items (20).

B27. The cargo aerial delivery system (10) of paragraph B26, wherein theone or more delivery items (20) includes two or more delivery items(20), and wherein the delivery system controller (60) is configured togenerate the delivery itinerary (30) such that the two or more deliveryitems (20) are delivered to the respective delivery destinations (22) atleast partially in order of decreasing hazardousness of the two or moredelivery items (20).

B28. The cargo aerial delivery system (10) of any of paragraphs B19-B27,wherein the delivery system controller (60) is configured to generatethe delivery itinerary (30) based, at least in part, on a/the timesensitivity information regarding each delivery item (20) of the one ormore delivery items (20).

B29. The cargo aerial delivery system (10) of paragraph B28, wherein theone or more delivery items (20) includes two or more delivery items(20), and wherein the delivery system controller (60) is configured togenerate the delivery itinerary (30) such that the two or more deliveryitems (20) are delivered to the respective delivery destinations (22) atleast partially in order of descending time sensitivity of the two ormore delivery items (20).

B30. The cargo aerial delivery system (10) of any of paragraphs B1-B29,wherein the UAV (200) includes a/the cargo container receiver (212)configured to selectively and operatively engage the cargo container(100) such that the cargo container (100) is secured to the UAV (200)and such that the UAV (200) may carry the cargo container (100).

B31. The cargo aerial delivery system (10) of paragraph B30, wherein thecargo container (100) includes a/the vehicle engagement structure (160)configured to selectively and operatively engage the cargo containerreceiver (212) to operatively secure the cargo container (100) to theUAV (200).

B32. The cargo aerial delivery system (10) of paragraph B31, wherein oneor both of the vehicle engagement structure (160) and the cargocontainer receiver (212) is at least partially load-bearing when thevehicle engagement structure (160) operatively engages the cargocontainer receiver (212).

B33. The cargo container (100) of paragraph B32, wherein the cargocontainer receiver (212) is configured to at least partially support aweight of the cargo container (100) when the vehicle engagementstructure (160) operatively engages the cargo container receiver (212)and when the vehicle (200) carries the cargo container (100).

B34. The cargo container (100) of any of paragraphs B32-B33, wherein thevehicle engagement structure (160) is configured to at least partiallysupport a weight of the vehicle (200) when the vehicle engagementstructure (160) operatively engages the cargo container receiver (212)and when the cargo container (100) rests upon a ground surface.

B35. The cargo container (100) of paragraph B34, wherein the cargocontainer (100) is configured to support the vehicle (200) above theground surface when the vehicle engagement structure (160) operativelyengages the cargo container receiver (212) and when the cargo container(100) rests upon the ground surface.

B36. The cargo aerial delivery system (10) of any of paragraphs B30-B35,wherein the cargo container (100) is configured to be selectivelytransitioned between a docked configuration, in which the cargocontainer receiver (212) operatively engages the cargo container (100)such that the UAV (200) may carry the cargo container (100), and anundocked configuration, in which the cargo container (100) is removedfrom the UAV (200).

B37. The cargo aerial delivery system (10) of paragraph B36, wherein thecargo container receiver (212) is configured to at least partiallyrestrict the cargo container (100) from transitioning from the dockedconfiguration to the undocked configuration.

B38. The cargo aerial delivery system (10) of any of paragraphs B36-B37,wherein the vehicle engagement structure (160) is configured to at leastpartially restrict the cargo container (100) from transitioning from thedocked configuration to the undocked configuration. B39. The cargoaerial delivery system (10) of any of paragraphs B36-B38, when dependentfrom paragraph B31, wherein the cargo container (100) is restricted fromtransitioning from the undocked configuration to the dockedconfiguration unless the vehicle engagement structure (160) and thecargo container receiver (212) are in a predetermined orientationrelative to one another.

B40. The cargo aerial delivery system (10) of any of paragraphs B36-B39,further comprising a/the cargo container engagement sensor (214)configured to detect when the cargo container (100) is in the dockedconfiguration.

B41. The cargo aerial delivery system (10) of paragraph B40, wherein oneor both of the cargo container receiver (212) and the vehicle engagementstructure (160) includes the cargo container engagement sensor (214).

B42. The cargo aerial delivery system (10) of any of paragraphs B40-B41,wherein the local communication mode (50) is utilized to initiatetransfer of the delivery information (140) from the containercommunication device (150) to the vehicle communication device (250)responsive to the cargo container engagement sensor (214) indicatingthat the cargo container (100) is in the docked configuration.

B43. The cargo aerial delivery system (10) of any of paragraphs B1-B42,further comprising a ground-based control system (12) configured tomonitor the UAV (200), and wherein the UAV (200) includes a groundcommunication device (220) configured to communicate with theground-based control system (12).

B44. The cargo aerial delivery system (10) of paragraph B43, wherein theground-based control system (12) is configured to monitor, viacommunication with the ground communication device (220), a location ofthe UAV (200).

B45. The cargo aerial delivery system (10) of any of paragraphs B43-B44,wherein the ground-based control system (12) is configured to monitor,via communication with the ground communication device (220), a deliverystatus of the one or more delivery items (20) carried by the UAV (200).

B46. The use of the cargo aerial delivery system (10) of any ofparagraphs B1-B45 to deliver one or more delivery items (20) to one ormore delivery destinations (22).

C1. A method (300) of utilizing a cargo aerial delivery system (10) thatincludes a cargo container (100) and an unmanned aerial vehicle (UAV)(200) to deliver one or more delivery items (20) to respective deliverydestinations (22), the method comprising:

loading (310) the one or more delivery items (20) into a container body(110) of the cargo container (100);

entering (320) the manifest information (130) regarding each deliveryitem (20) of the one or more delivery items (20) into a programmabledevice (120) of the cargo container (100);

operatively engaging (330) the cargo container (100) with the UAV (200);

generating (350) a delivery itinerary (30) for delivering each of theone or more delivery items (20) to the respective delivery destinations(22);

transporting (360) the cargo container (100) with the UAV (200)according to the delivery itinerary (30); and

unloading (370) each of the one or more delivery items (20) at therespective delivery destinations (22).

C2. The method (300) of paragraph C1, wherein the cargo aerial deliverysystem (10) is the cargo aerial delivery system (10) of any ofparagraphs B1-B46.

C3. The method (300) of any of paragraphs C1-C2, wherein the entering(320) the manifest information (130) into the programmable device (120)includes scanning each of the one or more delivery items (20) with aninput scanner (124).

C4. The method (300) of any of paragraphs C1-C3, wherein the entering(320) the manifest information (130) into the programmable device (120)includes manually entering the manifest information (130) via a/the userinterface (126).

C5. The method (300) of any of paragraphs C1-C4, wherein the engaging(330) the cargo container (100) with the UAV (200) includes engaging thecargo container (100) with a/the cargo container receiver (212) totransition the cargo container (100) from a/the undocked configurationto a/the docked configuration.

C6. The method (300) of paragraph C5, wherein the engaging the cargocontainer (100) with the cargo container receiver (212) includes formingan electrical connection between a/the vehicle communication device(250) and a/the container communication device (150).

C7. The method (300) of any of paragraphs C5-C6, wherein the engagingthe cargo container (100) with the cargo container receiver (212)includes generating and transmitting (332) an engagement signal witha/the cargo container engagement sensor (214) indicating that the cargocontainer (100) is in the docked configuration.

C8. The method (300) of paragraph C7, wherein the generating andtransmitting (332) the engagement signal includes transmitting theengagement signal to a/the container communication device (150).

C9. The method (300) of any of paragraphs C7-C8, wherein the generatingand transmitting (332) the engagement signal includes transmitting theengagement signal to a/the vehicle communication device (250).

C10. The method (300) of any of paragraphs C1-C9, further comprising,subsequent to the entering (320) the manifest information (130),transferring (340) delivery information (140) from the cargo container(100) to the UAV (200), wherein the delivery information (140) is based,at least in part, on the manifest information (130).

C11. The method (300) of paragraph C10, wherein the transferring (340)the delivery information (140) includes transferring the deliveryinformation (140) from a/the container communication device (150) toa/the vehicle communication device (250).

C12. The method (300) of paragraph C11, wherein the transferring (340)the delivery information (140) is performed via a wired connectionbetween the container communication device (150) and the vehiclecommunication device (250).

C13. The method (300) of any of paragraphs C11-C12, wherein thetransferring (340) the delivery information (140) is performed via awireless connection between the container communication device (150) andthe vehicle communication device (250).

C14. The method (300) of any of paragraphs C10-C13, when dependent fromparagraph C7, wherein the transferring (340) the delivery information(140) is performed responsive to the cargo container engagement sensor(214) indicating that the cargo container (100) is in the dockedconfiguration.

C15. The method (300) of paragraph C14, wherein the generating andtransmitting (332) the engagement signal with the cargo containerengagement sensor (214) includes transmitting the engagement signal tothe container communication device (150), and wherein the containercommunication device (150) initiates the transferring (340) the deliveryinformation (140) from the cargo container (100) to the UAV (200) uponreceipt of the engagement signal.

C16. The method (300) of any of paragraphs C14-C15, wherein thegenerating and transmitting (332) the engagement signal with the cargocontainer engagement sensor (214) includes transmitting the engagementsignal to the vehicle communication device (250), and wherein thevehicle communication device (250) initiates the transferring (340) thedelivery information (140) from the cargo container (100) to the UAV(200) upon receipt of the engagement signal.

C17. The method (300) of any of paragraphs C1-C16, wherein thegenerating (350) the delivery itinerary (30) is performed by a/thedelivery system controller (60).

C18. The method (300) of paragraph C17, wherein the UAV (200) includesthe delivery system controller (60), and wherein the generating (350)the delivery itinerary (30) is performed subsequent to the transferring(340) the delivery information (140) from the cargo container (100) tothe UAV (200).

C19. The method (300) of any of paragraphs C1-C18, wherein thegenerating (350) the delivery itinerary (30) is performed subsequent toa/the cargo container engagement sensor (214) generating andtransmitting (332) a/the engagement signal.

C20. The method (300) of any of paragraphs C1-C19, wherein thegenerating (350) the delivery itinerary (30) includes calculating (352)an optimal delivery route (32).

C21. The method (300) of paragraph C20, wherein the one or more deliveryitems (20) include two or more delivery items (20), wherein thecalculating (352) the optimal delivery route (32) includes calculating(354) a priority score associated with each of the two or more deliveryitems (20), and wherein the generating (350) the delivery itinerary (30)includes configuring the delivery itinerary (30) to deliver the two ormore delivery items (20) in order of descending priority score.

C22. The method (300) of paragraph C21, wherein the priority score of agiven delivery item (20) of the two or more delivery items (20) is atleast partially based upon a/the item weight information correspondingto the given delivery item (20).

C23. The method (300) of paragraph C22, wherein the priority score ofthe given delivery item (20) is positively correlated with a/the weightof the given delivery item (20).

C24. The method (300) of any of paragraphs C21-C23, wherein the priorityscore of a given delivery item (20) of the two or more delivery items(20) is at least partially based upon a/the hazardous materialinformation corresponding to the given delivery item (20).

C25. The method (300) of paragraph C24, wherein the priority score ofthe given delivery item (20) is positively correlated with a/thehazardousness of the given delivery item (20).

C26. The method (300) of any of paragraphs C21-C25, wherein the priorityscore of a given delivery item (20) of the two or more delivery items(20) is at least partially based upon a/the item destination informationcorresponding to the given delivery item (20).

C27. The method (300) of paragraph C26, wherein the priority score ofthe given delivery item (20) is negatively correlated with a distancebetween the UAV (200) and the delivery destination (22) of the givendelivery item (20).

C28. The method (300) of any of paragraphs C26-C27, wherein the priorityscore of the given delivery item (20) is positively correlated with thenumber of other delivery items (20) that have the same deliverydestination (22) as the given delivery item (20).

C29. The method (300) of any of paragraphs C21-C28, wherein the priorityscore of a given delivery item (20) of the two or more delivery items(20) is at least partially based upon a/the time sensitivity informationcorresponding to the given delivery item (20).

C30. The method (300) of paragraph C29, wherein the priority score ofthe given delivery item (20) is negatively correlated with a timeinterval between a present time and a/the latest arrival time by whichthe given delivery item (20) needs to reach the respective deliverydestination (22).

C31. The method (300) of any of paragraphs C21-C30, wherein the priorityscore of a given delivery item (20) of the two or more delivery items(20) is at least partially based upon a/the item recipient informationcorresponding to the given delivery item (20).

C32. The method (300) of paragraph C31, wherein the priority score ofthe given delivery item (20) is positively correlated with the number ofother delivery items (20) that have the same intended recipient as thegiven delivery item (20).

As used herein, the phrase “at least substantially,” when modifying adegree or relationship, includes not only the recited “substantial”degree or relationship, but also the full extent of the recited degreeor relationship. A substantial amount of a recited degree orrelationship may include at least 75% of the recited degree orrelationship. For example, a first direction that is at leastsubstantially parallel to a second direction includes a first directionthat is within an angular deviation of 22.5° relative to the seconddirection and also includes a first direction that is identical to thesecond direction.

As used herein, the terms “selective” and “selectively,” when modifyingan action, movement, configuration, or other activity of one or morecomponents or characteristics of an apparatus, mean that the specificaction, movement, configuration, or other activity is a direct orindirect result of user manipulation of an aspect of, or one or morecomponents of, the apparatus.

As used herein, the terms “adapted” and “configured” mean that theelement, component, or other subject matter is designed and/or intendedto perform a given function. Thus, the use of the terms “adapted” and“configured” should not be construed to mean that a given element,component, or other subject matter is simply “capable of” performing agiven function but that the element, component, and/or other subjectmatter is specifically selected, created, implemented, utilized,programmed, and/or designed for the purpose of performing the function.It is also within the scope of the present disclosure that elements,components, and/or other recited subject matter that is recited as beingadapted to perform a particular function may additionally oralternatively be described as being configured to perform that function,and vice versa. Similarly, subject matter that is recited as beingconfigured to perform a particular function may additionally oralternatively be described as being operative to perform that function.

As used herein, the term “and/or” placed between a first entity and asecond entity means one of (1) the first entity, (2) the second entity,and (3) the first entity and the second entity. Multiple entries listedwith “and/or” should be construed in the same manner, i.e., “one ormore” of the entities so conjoined. Other entities optionally may bepresent other than the entities specifically identified by the “and/or”clause, whether related or unrelated to those entities specificallyidentified. Thus, as a non-limiting example, a reference to “A and/orB,” when used in conjunction with open-ended language such as“comprising,” may refer, in one example, to A only (optionally includingentities other than B); in another example, to B only (optionallyincluding entities other than A); in yet another example, to both A andB (optionally including other entities). These entities may refer toelements, actions, structures, steps, operations, values, and the like.

As used herein, the phrase “at least one,” in reference to a list of oneor more entities should be understood to mean at least one entityselected from any one or more of the entities in the list of entities,but not necessarily including at least one of each and every entityspecifically listed within the list of entities and not excluding anycombinations of entities in the list of entities. This definition alsoallows that entities may optionally be present other than the entitiesspecifically identified within the list of entities to which the phrase“at least one” refers, whether related or unrelated to those entitiesspecifically identified. Thus, as a non-limiting example, “at least oneof A and B” (or, equivalently, “at least one of A or B,” or,equivalently “at least one of A and/or B”) may refer, in one embodiment,to at least one, optionally including more than one, A, with no Bpresent (and optionally including entities other than B); in anotherembodiment, to at least one, optionally including more than one, B, withno A present (and optionally including entities other than A); in yetanother embodiment, to at least one, optionally including more than one,A, and at least one, optionally including more than one, B (andoptionally including other entities). In other words, the phrases “atleast one,” “one or more,” and “and/or” are open-ended expressions thatare both conjunctive and disjunctive in operation. For example, each ofthe expressions “at least one of A, B, and C,” “at least one of A, B, orC,” “one or more of A, B, and C,” “one or more of A, B, or C,” and “A,B, and/or C” may mean A alone, B alone, C alone, A and B together, A andC together, B and C together, A, B, and C together, and optionally anyof the above in combination with at least one other entity.

As used herein, the phrase, “for example,” the phrase, “as an example,”and/or simply the term “example,” when used with reference to one ormore components, features, details, structures, embodiments, and/ormethods according to the present disclosure, are intended to convey thatthe described component, feature, detail, structure, embodiment, and/ormethod is an illustrative, non-exclusive example of components,features, details, structures, embodiments, and/or methods according tothe present disclosure. Thus, the described component, feature, detail,structure, embodiment, and/or method is not intended to be limiting,required, or exclusive/exhaustive; and other components, features,details, structures, embodiments, and/or methods, including structurallyand/or functionally similar and/or equivalent components, features,details, structures, embodiments, and/or methods, are also within thescope of the present disclosure.

In the present disclosure, several of the illustrative, non-exclusiveexamples have been discussed and/or presented in the context of flowdiagrams, or flow charts, in which the methods are shown and describedas a series of blocks, or steps. Unless specifically set forth in theaccompanying description, it is within the scope of the presentdisclosure that the order of the blocks may vary from the illustratedorder in the flow diagram, including with two or more of the blocks (orsteps) occurring in a different order, concurrently, and/or repeatedly.It is also within the scope of the present disclosure that the blocks,or steps, may be implemented as logic, which also may be described asimplementing the blocks, or steps, as logics. In some applications, theblocks, or steps, may represent expressions and/or actions to beperformed by functionally equivalent circuits or other logic devices.The illustrated blocks may, but are not required to, representexecutable instructions that cause a computer, processor, and/or otherlogic device to respond, to perform an action, to change states, togenerate an output or display, and/or to make decisions.

The various disclosed elements of apparatuses and systems and steps ofmethods disclosed herein are not required to all apparatuses, systems,and methods according to the present disclosure, and the presentdisclosure includes all novel and non-obvious combinations andsubcombinations of the various elements and steps disclosed herein.Moreover, one or more of the various elements and steps disclosed hereinmay define independent inventive subject matter that is separate andapart from the whole of a disclosed apparatus, system, or method.Accordingly, such inventive subject matter is not required to beassociated with the specific apparatuses, systems, and methods that areexpressly disclosed herein and such inventive subject matter may findutility in apparatuses, systems, and/or methods that are not expresslydisclosed herein.

1. A cargo aerial delivery system for delivering one or more delivery items to one or more delivery destinations, the cargo aerial delivery system comprising: a cargo container configured to carry the one or more delivery items; and an unmanned aerial vehicle (UAV) configured to carry the cargo container to each of the one or more delivery destinations corresponding to the one or more delivery items; wherein the cargo container includes a programmable device that stores manifest information regarding each of the one or more delivery items; wherein the manifest information includes item destination information that represents a respective delivery destination of each of the one or more delivery items; wherein the cargo aerial delivery system further utilizes a local communication mode configured to convey delivery information from the cargo container to the UAV, and wherein the delivery information is based, at least in part, on the item destination information.
 2. The cargo aerial delivery system of claim 1, wherein the local communication mode is utilized to convey the delivery information from the cargo container directly to the UAV independent of communications with an external remotely-located communication network.
 3. The cargo aerial delivery system of claim 1, wherein the UAV includes a vehicle communication device, wherein the cargo container includes a container communication device, and wherein the local communication mode is utilized to transfer the delivery information from the container communication device to the vehicle communication device via one or more of an electromagnetic signal, an electrical signal, a radio frequency signal, a near-field communication signal, an optical signal, a wireless connection, a wired connection, a direct connection, or a visual connection.
 4. The cargo aerial delivery system of claim 1, further comprising a delivery system controller configured to generate a delivery itinerary for the UAV to travel along to deliver the one or more delivery items, wherein the delivery itinerary is based, at least in part, on the manifest information.
 5. The cargo aerial delivery system of claim 4, wherein the UAV includes the delivery system controller.
 6. The cargo aerial delivery system of claim 4, wherein the cargo container includes the delivery system controller.
 7. The cargo aerial delivery system of claim 4, wherein the one or more delivery items include two or more delivery items; wherein the manifest information further includes item weight information that represents a weight of each of the two or more delivery items; wherein the delivery system controller is configured to generate the delivery itinerary based, at least in part, on the item weight information regarding each of the two or more delivery items for each delivery destination; and wherein the delivery system controller is configured to generate the delivery itinerary such that the two or more delivery items are delivered to the respective delivery destinations at least partially in order of descending weight of the two or more delivery items for each delivery destination.
 8. The cargo aerial delivery system of claim 1, wherein the cargo container includes a vehicle engagement structure, and wherein the UAV includes a cargo container receiver configured to selectively engage the vehicle engagement structure such that the cargo container is secured to the UAV and such that the UAV may carry the cargo container.
 9. The cargo aerial delivery system of claim 8, wherein the cargo container is configured to be selectively transitioned between a docked configuration, in which the cargo container receiver operatively engages the cargo container such that the UAV may carry the cargo container, and an undocked configuration, in which the cargo container is removed from the UAV; and wherein the cargo aerial delivery system further comprises a cargo container engagement sensor configured to detect when the cargo container is in the docked configuration.
 10. The cargo aerial delivery system of claim 9, wherein one or both of the cargo container receiver and the vehicle engagement structure includes the cargo container engagement sensor.
 11. The cargo aerial delivery system of claim 9, wherein the local communication mode is utilized to initiate transfer of the delivery information from a container communication device to a vehicle communication device responsive to the cargo container engagement sensor indicating that the cargo container is in the docked configuration.
 12. The cargo aerial delivery system of claim 1, wherein the UAV is a rotorcraft with one or more rotors.
 13. A method of utilizing the cargo aerial delivery system of claim 1 to deliver the one or more delivery items to the one or more delivery destinations, the method comprising: loading the one or more delivery items into a container body of the cargo container; entering the manifest information regarding each of the one or more delivery items into the programmable device of the cargo container; operatively engaging the cargo container with the UAV; generating a delivery itinerary for delivering each of the one or more delivery items to the respective delivery destination; transporting the cargo container with the UAV according to the delivery itinerary; and unloading each of the one or more delivery items at the respective delivery destination.
 14. The method of claim 13, wherein the entering the manifest information into the programmable device includes scanning each of the one or more delivery items with an input scanner.
 15. The method of claim 13, wherein the entering the manifest information into the programmable device includes manually entering the manifest information via a user interface.
 16. The method of claim 13, wherein the engaging the cargo container (100) with the UAV includes engaging the cargo container with a cargo container receiver to transition the cargo container from an undocked configuration, in which the cargo container is removed from the UAV, to a docked configuration, in which the cargo container receiver operatively engages the cargo container such that the UAV may carry the cargo container.
 17. The method of claim 16, wherein the engaging the cargo container with the cargo container receiver includes generating and transmitting an engagement signal with a cargo container engagement sensor indicating that the cargo container is in the docked configuration.
 18. The method of claim 17, further comprising, subsequent to the entering the manifest information, transferring delivery information from the cargo container to the UAV, wherein the delivery information is based, at least in part, on the manifest information, and wherein the transferring the delivery information is performed responsive to the cargo container engagement sensor indicating that the cargo container is in the docked configuration.
 19. The method of claim 13, wherein the one or more delivery items include two or more delivery items, wherein the generating the delivery itinerary includes calculating an optimal delivery route, wherein the calculating the optimal delivery route includes calculating a priority score associated with each of the two or more delivery items, and wherein the generating the delivery itinerary includes configuring the delivery itinerary to deliver the two or more delivery items in order of descending priority score.
 20. The method of claim 19, wherein the manifest information includes item weight information that represents a weight of each of the two or more delivery items; wherein the priority score of a given delivery item of the two or more delivery items is at least partially based upon the item weight information corresponding to the given delivery item; and wherein the priority score of the given delivery item is positively correlated with the weight of the given delivery item. 